BBS Toolkit/BBS Toolkit.iso/doors_1/jlut500.zip/HLP.ZIP/GENERAL.HLP

Text File | 1992-07-20 | 20KB | 548 lines

┌─────────────────────────────────────────────────────────────────────────────┐
│ General Informations about THE JL's.........................................│
└─────────────────────────────────────────────────────────────────────────────┘

                   ╔════════════════════════════════╗
                   ║ READING THIS FILE IS IMPORTANT ║
                   ╚════════════════════════════════╝

                     Contents
                     ───────────────────────────────
                   ■ Description of general options
                   ■ CONFIG.SYS
                   ■ JL.CNF
                   ■ JLPATH within your environment
                   ■ Limitations
                   ■ General parameters
                   ■ General things
                   ■ ERROR CODES



Here you find informations about general options, limitations, JL.CNF
and how to set the JLPATH Environment Variable.

JLUTIL is an Utility from Juergen Lorenz, Germany. It is compiled with
the latest version of Turbo Pascal and includes several powerful options.
Start JLUTIL with the available options.

     e.g.       JLUTIL /DC
     or         JLUTIL /IL /AN /DM ?,30 /SU

The program has access to the environment, so you can start JLUTIL
from any directory, if you have specified the GT-Directory with
SET GTPATH= and the JL-Directory with SET JLPATH= Command.

You can redirect the input and/or the output and you can use JLUTIL
remotely.

     e.g.       JLUTIL /DM  < TEST01.BEH
     or         JLUTIL /AN  > ANALYSIS.TXT

Most of the JLUTIL-Activities are logged into a file called JL.LOG.
If you want to have Extended Logging you must set in JL.CNF EL=TRUE.

Within the file JL.CTL are some informations stored about the usage of
JLUTIL. /AN -J sends me the content as a msg. JLUTIL sends me sometimes
automatically a report. This helps me to enhance JLUTIL and to see,
which options are in use and which aren't. Also i get a feeling, how
many people are using JLUTIL.





┌─Description of general options─────────────────────────────────────────────┐
└────────────────────────────────────────────────────────────────────────────┘

  The following general options can be used every time, you are running
  THE JL's.


┌─────────────────────┐
│ /DATE i,..,j[k,..m] │
└─────────────────────┘

   i is a day, k a weekday. You can specify at which date JLUTIL will be
   executed, eg JLUTIL /IL -M /DATE 1, this will produce a monthly report,
   if it is the first day of the month. The format is:  /DATE days delimited
   with commas and followed with the weekdays in brackets.
   eg JLUTIL /MO /DATE 1,15[1]  This will run the Register-Module at every
   first and the 15th day of a month and at every Sunday.  (Sunday[1] ..
   Saterday[7]).  eg JLUTIL /AN /DATE [1]  makes an analysis at every Sunday.


┌────────┐
│ /DEBUG │
└────────┘

   displays passed marks (only for Error trapping). You can see which files
   JLUTIL assigns and closes.  Run eg. JLUTIL /AN /DEBUG


┌────────┐
│ /PAUSE │
└────────┘

   If you insert this parameter, JLUTIL will pause after  24 lines.


┌─────────┐
│ /EXTLOG │
└─────────┘

   Force ExtendedLog. Or use the EL= Line within JL.CNF.


┌───────────────┐
│ /SKIPCNFCHECK │
└───────────────┘

   Forces the JL's to skip the check of JL.CNF and GT.CNF for unknown or
   double variables.


┌───────┐
│ /!001 │
└───────┘

   You can setup a File for each option. The Name is JL{xx}.TXT, where xx
   stands for the name of the option. This File will be displayed after
   the JLHeader, if it exists and you specify this general parameter,
   and after displaying this File, the User will be asked, if he wants to
   continue. This helps you to explain each option.


┌───────┐
│ /!002 │
└───────┘

   Use this general option, if you get a TP Error 203 (Heap Overflow).
   THE JL's will not copy JL.MSG to the heap, if this option is used.


┌───────┐
│ /!003 │
└───────┘

   If you use this parameter, THE JL's skip reading GTUSER.BBS. They
   set the actual user to SA= in JL.CNF and give him level [0] and the
   authorization [SY].


┌───────┐
│ /!004 │
└───────┘

   Normally THE JL's try to use EMS, if available. Normally this works,
   if you have EMS or not. But if strange things happen during the check
   for EMS, you should specify /!004. This will force THE JL's not to try
   to use EMS.



┌─CONFIG.SYS─────────────────────────────────────────────────────────────────┐
└────────────────────────────────────────────────────────────────────────────┘

  THE JL's open some Files and need ANSI.SYS. Please insert the following
  lines into your CONFIG.SYS.

                         ┌CONFIG.SYS──────────────────┐
                         │                            │
                         │  DEVICE   = ANSI.SYS       │
                         │  FILES    = 50  {or more}  │
                         └────────────────────────────┘


┌─JL.CNF─────────────────────────────────────────────────────────────────────┐
└────────────────────────────────────────────────────────────────────────────┘

In position  1-2 of  each record  in the configuration file is a code to
identify a parameter.    After  the  "=",  the  value  of  the parameter
appears. You can specify a value, but it is not necessary. But if a
variable is missing, THE JL's will quit with an error. So you have to
insert all variables, but you can leave them blank.


┌──────────────────────────────┐
│ Serial-specific informations │
└──────────────────────────────┘

  SA=Your Name              SystemAdministrator
  SO=ALL                    Registered Options.
  SN=000000                 SerialNumber
  SC=xxxx-yyyy              SerialNumber CRC, if known
  NC=xxxx-yyyy              Local NetMail Coordinator CRC, if known
  DC=xxxx-yyyy              Distributor CRC, if known


┌───────────────────┐
│ Names of CoSysops │
└───────────────────┘

  MM=Name of CoSysop        CoSysop for Msgs
  UM=Name of CoSysop        CoSysop for Users
  FM=Name of CoSysop        CoSysop for Files
  PF=Juergen Lorenz         JLUTIL sends me a MSG, if an Error occurs
                            (Not in Use at this time)


┌──────────────────┐
│ GT Compatibility │
└──────────────────┘

  GT=17                     GT-Version IN [0,14,15,16,17]
                            If you specify GT=0, THE JL's are running in
                            local mode. They don't need GT. Everybody, if
                            he has a GT BBS installed or not, can run THE
                            JL's then, but of course only options, which
                            don't need GT.
                            If you set GT to 17, JLUTIL will set the
                            GTVersion internally back to 16.


┌──────────────────────┐
│ Variables for JLBANK │
└──────────────────────┘

  CL=A..Z                   Contribution-Levels for JLBANK


┌──────────────────────┐
│ Variables for JLPLOT │
└──────────────────────┘

  OD=01-01-89               Date for JLCALL1.LOG, JLCALL2.LOG and
                            JLREAD.LOG. JLUTIL loggs the number of
                            days between this and the actual date.


┌─────────────────────────┐
│ Directories for the MCS │
└─────────────────────────┘

  M1=E:\GT\MCSUSER          The MCS writes UserMsgs  into this MSG-Area
  M2=E:\GT\MCSSYSOP         The MCS writes SysopMsgs into this MSG-Area
  M3=E:\GT\MAILING          The MailingLists writes Msgs into this
                            MSG-Area

┌───────────────┐
│ Miscellaneous │
└───────────────┘

  DI=1                      Display:  1  Normal  (redirectable)
                                      2  Faster  (local mode, not redirectable)

  MD=C                      MAIL-DRIVE (here are \MAILOUT etc.)
  ZP=C:\TOOLS\              ZIP-PATH   (here are PKZIP.EXE and PKUNZIP.EXE)

  MP=C:\JLUTIL\MSG\         MSG-Path   (here are 00= to ...)
  HP=C:\JLUTIL\HLP\         HLP-Path   (here are all *.HLP Files from THE JL's)
  LP=C:\JLUTIL\LOG\         LOG-Path   (here are LogFiles, L1= to ...)
  QP=C:\JLUTIL\QST\         QST-Path   (here are all QUEST*.* Files for /QU)
  TP=C:\JLUTIL\MLT\         MLT-Path   (here are all *.@ML files for /ML)
  BP=C:\JLUTIL\BANK         The homedirectory of JLBANK.

                            If you have specified HP=D:\JLUTIL\HLP\ then
                            JLUTIL searches the *.HLP files within
                            C:\JLUTIL\HLP\*.HLP.

  EL=TRUE                   EXTENDED LOGGING  True OR False
  PL=4                      Minimum Password Length (for /IP /CU)
  PH=TRUE                   Display PhoneNumber (for /SU /MC)  TRUE or FALSE
  AN=TRUE                   ANSI:  TRUE / FALSE / CALLER
  TO=5                      TimeOut in minutes
  CU=                       Currency (for /IL and JLBANK) eg. DM, $US
  ED=INTERNAL               Name of your Editor (including Path)
                            eg: ED=C:\TOOLS\Q.EXE
                            or: ED=INTERNAL  if you want to use the
                                             internal Editor.
  DE=                       DefaultCommandLine, if the CommandLine is
                            empty. If you entering at the DOS Prompt
                            JLUTIL without any parameters, JLUTIL
                            will do, what is specified here. If DE=/HE,
                            it will run HE.
  KI=TRUE                   Can be TRUE or FALSE. With this variable
                            you can determine, if Users with invalid
                            levels will be killed - if KI=TRUE - or
                            not - if KI=FALSE.

┌───────────────┐
│ Message-Files │
└───────────────┘

  JLUTIL sends the ??????_U.MSG Files to the User and the
  ??????_S.MSG Files to the Sysop. You can add - separated
  with a komma - the subject of the message. This Subject
  can include variables like @RFN, etc. For options like IL.


  MO=CHANGE OF YOUR LEVEL   Subject of the MO option Messages
  00=UNKNOW_U.MSG
  01=BADPSW_S.MSG,BAD PASSWORDS
  02=BADPSW_U.MSG,HACKING FOR YOU !!!
  03=DENIED_S.MSG
  04=DENIED_U.MSG
  05=DLLOAD_S.MSG
  06=DLLOAD_U.MSG
  07=UPLOAD_S.MSG
  08=UPLOAD_U.MSG,Thx, @RFN @RLN
  09=ANSWER_U.MSG
  10=TRASH_S .MSG
  11=CHNGEPSW.MSG
  12=TOADMIN .001
  13=CHNG_LVL.MSG
  14=USDTIM_S.MSG
  15=USDTIM_U.MSG
  16=MISC_S  .MSG
  17=MISC_U  .MSG
  18=DORUSE_S.MSG
  19=DORUSE_U.MSG
  20=INVOIC_U.MSG
  21=TOSENDER.MSG


┌───────────────────┐
│ Name of LOG-Files │
└───────────────────┘

  Please don't change the following settings. If you want to change
  L2= to L3= then use names with the following format:

  Path\??????I.???         I is 1 for L2=  and I = 2 for L3=


  L1=JL      .LOG
  L2=JLCALL1 .LOG           \
  L3=JLCALL2 .LOG            >-- for JLPLOT
  L4=JLREAD  .LOG           /
  L5=JLBANK  .LOG           ---- for JLBANK
  P1=PAY1.MSG               \
  P2=PAY2.MSG                >-- for JLBANK
  P3=PAY3.MSG               /


┌────────────────────┐
│ Colors of THE JL's │
└────────────────────┘

  If you don't insert the following variables, JLUTIL uses the
  GT Colors from GT.CNF. You can overwrite the GT Colors with
  specifying different values within JL.CNF.


            ┌─Color Number Table─────────────────────┐
            │                                        │
            │ Dark Colors         Light Colors       │
            │ ════════════════    ══════════════════ │
            │ 0 : Black           8  : Dark Gray     │
            │ 1 : Blue            9  : Light Blue    │
            │ 2 : Green           10 : Light Green   │
            │ 3 : Cyan            11 : Light Cyan    │
            │ 4 : Red             12 : Light Red     │
            │ 5 : Magenta         13 : Light Magenta │
            │ 6 : Brown           14 : Yellow        │
            │ 7 : Light Gray      15 : White         │
            └────────────────────────────────────────┘


  WF= Window foreground color number.  Anyone of the 16 values from the
      table above.
  WB= Window background color number.  Anyone of the DARK shades, 0-7,
      from the table above.
  WR= Window-frame foreground color number.  Anyone of the 16 values
      from the table above.
  WS= Window-frame background color number.  Anyone of the DARK shades
                 from the table above.
  HF= Option hi-lite color, foreground.
  HB= Option hi-lite color, background.
  OF= Option lo-lite color, foreground.
  OB= Option lo-lite color, background.
  TF= Status line color, foreground.
  TB= Status line color, background.
  WU= Window Title color, foreground.
  WV= Window Title color, background.
  DU= Phone directory hi-lite color, foreground.
  DV= Phone directory hi-lite color, background.



┌─JLPATH within your environment─────────────────────────────────────────────┐
└────────────────────────────────────────────────────────────────────────────┘

Please set the JLPATH= Variable with the SET Command:

    e.g.   SET JLPATH=_______________ to the home directory of THE JL's.


The specified directory is the home directory of JLUTIL. Here must
be all JLUTIL Files. Put this commandline into your AUTOEXEC.BAT.




┌─Limitations────────────────────────────────────────────────────────────────┐
└────────────────────────────────────────────────────────────────────────────┘

  ■        200 User   large PickLists
  ■       ---- KB     Undelimited Editor
  ■   1.1e4932 Calls  Display Calls




┌─General parameters─────────────────────────────────────────────────────────┐
└────────────────────────────────────────────────────────────────────────────┘

┌─────────┐
│ MsgArea │
└─────────┘

  Here you can specify the [DosName] of the MsgArea, or you
  specify [?] and choose the MsgArea from a menue. If you want,
  you can specify [~] to select the NetMailArea.



┌─General things─────────────────────────────────────────────────────────────┐
└────────────────────────────────────────────────────────────────────────────┘

THE JL's are assuming that they are in use by the logged on GTUser,
who is specified in GTUSER.BBS. If you are using THE JL's locally,
you have to change GTUSER.BBS. Perhaps you make your own GTUSER.MY
and if you want to use THE JL's you start a batch, which copies
GTUSER.MY to GTUSER.BBS before it runs THE JL's.



┌─ERROR CODES────────────────────────────────────────────────────────────────┐
└────────────────────────────────────────────────────────────────────────────┘

If an error occurs, please make use of the possibility to run THE JL's
in debug mode using the general parameter /DEBUG.

 1  The variable GTPATH= isn't specified within the environment.
    Enter GTPATH=xxx at the DOS prompt (xxx must be your GT directory).

 2  The variable STPATH= isn't specified within the environment.
    Enter STPATH=xxx at the DOS prompt (xxx must be your ST directory).

 3  The variable JLPATH= isn't specified within the environment.
    Enter JLPATH=xxx at the DOS prompt (xxx must be your JL directory).

 4  THE JL's want to delete a file, but this is impossible. Perhaps
    because it is readonly or the PATH is incorrect etc. Check the
    filename. Perhaps it was in use by another program. While trying
    to delete the file an ioerror happened.

 5  NOT IN USE.

 6  Read the Error-Message.

 7  THE JL's tried to convert a string to a number, which failed.
    Perhaps the string contains chars. Perhaps it exceeds the
    number format. Nevertheless, you can do nothing. Write me a
    short message.

 8  JL.CNF, GT.CNF or another configuration file contains a
    variable, which must be followed by a number. But within your
    configuration file this variable isn't set to a number.
    Perhaps it contains chars. Check the configuration file
    and search for the specified variable.

 9  THE JL's tries to use a number, but the number is out of range.
    Perhaps it exceeds the number format. Nevertheless, you can do
    nothing. Write me a short message. Perhaps you have set
    a variable within JL.CNF to an inpropper value. The error message
    contains the name of the procedure, in which the range error
    occured. Please give me this name too. This error means, that
    i have specified a value, which hasn't been specified in this
    procedure.

10  THE JL's looks for an operand, but can't find it. Nevertheless,
    you can do nothing. Write me a short message. Look into the HLP
    file, if this option needs an parameter, which you haven't
    specified.

11  NOT IN USE. (out of range ?)

12  Read the Error-Message.

13
14
15

16  Timeout. The JL's have detected a delay while waiting for an
    input, which was longer than specified in JL.CNF.

17  THE JL's want to print, but this is impossible. Perhaps the
    printer is offline or the connection between the computer
    and the printer is invalid.

18  THE JL's try to find a record in the GT-User database, but
    they don't find this record. Perhaps the index file must
    be reconstructed. Check, if you find the record of the
    specified Username in USER.CTL with a program like SYSOP.EXE.

19  THE JL's tried to read a file and detected an uninspected
    end of this file, so the format is invalid. This can happen,
    if you have specified a wrong GT Version (the length of user-
    record or a message-record are not identical between all GT Versions).
    Look at the specified file and check, if the file looks
    alright. An ioerror happened during reading the specified
    file.

20  A TurboPascal Error occured. If the TP error is #203, then use
    the general option /!002. Nevertheless, you can do nothing.
    Write me a short message with the errornumber of TurboPascal.

21  You specified a GT-version in JL.CNF, which is not valid.
    Look above, which settings are correct.

22  NOT IN USE.

23  THE JL's want to open a file, but this is impossible. Perhaps
    because the PATH is incorrect or the file doesn't exist. Please
    check the filename and look, if you have set the variables
    MP=, HP=, LP= and QP= within JL.CNF correctly. Look if you can
    find the specified file. Is the attribute perhaps hidden ?
    Is the file in use by another program, which doesn't close the
    file or give it free for writing ?

24

25  A line within JL.MSG hasn't been found. Your JL.MSG is invalid.
    Have you changed it ?  Look into the original JL.MSG and add
    this line.

26  A line within JL.MSG was empty. You have killed a line, and now
    this line is empty, but THE JL's need this line.

27  THE JL's tried to write to a file, which failed. An ioerror happened
    during writing to the specified file. Is this file perhaps read-only ?

28  THE JL's tried to get the filepos of a file, which failed. An ioerror
    happened during getting the filepos of the specified file. Is this file
    perhaps read-only or used by another program ?

29  THE JL's tried to seek a position in a file, which failed. An ioerror
    happened during seeking this position in the specified file. Is this file
    perhaps read-only or used by another program ?  Is this file too
    short ?

30  THE JL's tried to look, if the EOF of a file has been reached, which
    failed. An ioerror happened during this action. Is this file perhaps
    read-only or used by another program ?




┌────────────────────────────────────────────────────────────────────────────┐
└────────────────────────────────────────────────────────────────────────────┘

 Please read HISTORY.DOC too.